Part Number Hot Search : 
AD536AKH 600ETT SKY77633 NCP12 0E907 6341PC XT334Q ST10F269
Product Description
Full Text Search
 

To Download RN-4142-EK-UG Datasheet File

  If you can't view the Datasheet, Please click here to try to view without PDF Reader .  
 
 


  Datasheet File OCR Text:
  rn-41-ek & rn-42-ek evaluation kit user?s guide RN-4142-EK-UG ? 2012 roving networks. all rights reserved. RN-4142-EK-UG version 1.0 12/10/12
roving networks, inc. 102 cooper court los gatos, ca 95032 +1 (408) 395-5300 www.rovingnetworks.com copyright ? 2012 roving networks. all rights reserved. roving networks is a registered trademark of roving networks. apple inc., iphone, ipad, itunes, made for iphone are register ed trademarks of apple computer. roving networks reserves the right to make corrections , modifications, and other changes to its products, documentation and services at any time. customers should obtain the latest relevant information before plac- ing orders and should verify that such information is current and com- plete. roving networks assumes no liability for applications assistance or cus- tomer?s product design. customers ar e responsible for their products and applications that use roving netw orks components. to minimize cus- tomer product risks, customers shoul d provide adequate design and oper- ating safeguards. roving networks products are not authorized for use in safety-critical applications (such as life support) where a failure of the roving networks product would reasonably be expected to cause severe personal injury or death, unless officers of the parties have executed an agreement specifi- cally governing such use. www.rovingnetworks.com version 1.0 12/10/12 page 2
RN-4142-EK-UG www.rovingnetworks.com version 1.0 12/10/12 page 3 1.0 overview this document describes the hardware and software setup for roving networks rn-41-ek and rn-42-ek evaluation boards. the rn-41-ek and rn-42-ek evaluation boards are field-ready, bluetooth sig qualified prototyping platforms for the rn41 and rn42 modules, respectively. the boards have the flexibility to connect directly to pcs via a standard usb interface (via the ftdi chipset) or to embedded processors through the ttl uart interface. the status leds, dipswitches, and signal headers enable rapid prot otyping and integration into existing systems. you configure and control the modules from a console with a simple ascii command language. once the configuration is set up, the module ca n connect over bluetooth. you use the evaluation kit to configure the bluetooth module using t he command interface, create connections, and transfer data. see ?resources & related documents? on page 16 for information on available documentation. the rn-41-ek and rn-42-ek evaluati on boards support the serial po rt profile (spp) and human interface device (hid) profiles. the instructions in this document use the spp profile. for more information on these profiles and how to switch between them, refer to the bluetooth command reference & advanced information user?s guide . 2.0 evaluation kit description the evaluation kit includes the hardware requir ed to connect the evaluation board to your com- puter. see table 2-1 . to evaluate the module on the evaluation board, you need a computer with a usb port running the microsoft windows or mac os-x operating system. figure 2-1 describes the evaluation board?s interfaces and connectors. table 2-2 describes the status leds. the green led indicates the status of the bluetooth connection and when the device is in configuration mode. the rn41 and rn42 modules are pin co mpatiable; therefore, the description applies to both the rn-41-ek and rn-42-ek boards. refer to ?rn-41-ek & rn-42-ek schematic? on page 17 for the board?s schematic. note: before beginning your evaluation, you may need to install the ftdi driver for the usb cable. you can download the driver (as well as other tools and utilities) from the roving networks website at http://www.rovingnetworks.com/support.php . table 2-1: evaluation kit contents hardware description evaluation board contains the bluet ooth module, status leds, and dipswitches. mini-usb cable links your computer to the evaluation board.
RN-4142-EK-UG www.rovingnetworks.com version 1.0 12/10/12 page 4 figure 1-1: rn-41-ek & rn- 42-ek evaluation board, note 1 note 1: this figure shows the rn-42-ek board. the rn-41-ek board is similar. usb interface pcb trace antenna led indicators (s = green a = red) gpio signal header 2 (j2) gpio signal header 1 (j1) programming header (j3) top pin 13 pcb trace antenna configuration switches bottom gpio signal header 1 (j1) gpio signal header 2 (j2) programing header (j3) pin description pin description pin description 1 gpio6 13 gpio4 1 spi_miso 2 gpio7 14 gpio3 2 spi_mosi 3 reset_n 15 gpio2 3 spi_sck 4 no connect 16 cts 4 spi_ss 5 no connect 17 rts 5 3.3 v 6 no connect 18 txd 6 gnd 7 no connect 19 rxd 8 sensor input 1 (aio1) 20 gpio11 configuration switches 9 shutdown (shdn) 21 gpio10 switch description 10 no connect 22 gpio9 1 restore factory defaults 11 3.3 v 23 gpio8 2 automatic discovery 12 gnd 24 sensor input 0 (aio0) 3 automatic master 4 default baud rate 8 7 6 15 4 3 2 12 11 10 9 20 19 18 13 17 16 15 14 24 23 22 21 6 15 4 3 2
RN-4142-EK-UG www.rovingnetworks.com version 1.0 12/10/12 page 5 3.0 hardware setup to set up the evaluation hardware, perform the following steps: 1. connect the mini-usb cable to your com puter?s usb port and to the evaluation board?s mini-usb connector. this connection provides power to the board and provides a data connection to the command console. 2. note the com port to which you have attached the cable. figure 3-1 shows the completed hardware setup for the evaluation boards. figure 1-2: completed hardware setup table 2-2: status leds mode green led (s) red led (a) fast blink, 10 times per second command mode ? blinks twice per second boot up, remotely configurable ? blinks once per second discoverable/idle data over the uart solid on connected ? note: windows prompts you to install the ftdi dr ivers (that create a virtual com port to the module?s usb port) if they are not alr eady installed. you can download the driv- ers from the support page on the roving networks website at http://www.rovingnet- works.com/support.php .
RN-4142-EK-UG www.rovingnetworks.com version 1.0 12/10/12 page 6 4.0 using the evaluation kit you program roving networks bluetooth devices ov er the bluetooth link or through the serial interface (usb port) using a simple ascii comm and language, which is similar to the industry- standard hayes at protocol. set commands configure the module and get commands echo the current configuration. configur ation settings modified with the set command do not take effect until the module has been rebooted, even though the get command may show otherwise. this section assumes that you have a worki ng knowledge of bluetooth operation and communi- cations. to configure the roving networks devices you need a bluetooth-enabled pc (either built-in or using a usb bluetooth dongle). you ca n only configure one device at a time. once configured, device settin gs are saved (independent of power down) until they are explicitly changed or the factory defaults are restored. 4.1 command mode vs. data mode the bluetooth device operates in two modes: data mode (default) and command mode. upon power up the device is in data mode. while in data mode, the module is essentially a data pipe. when the module receives data from a remote bl uetooth device over a serial port profile (spp) connection, it strips the bluet ooth headers and trailers and passes the user data to the uart. when data is written to the uart, the module constructs the bluetooth packet and sends it out over the bluetooth spp co nnection. thus, t he entire process of sendi ng/receiving data to the host is transparent to the end microprocessor. see figure 1-1 . figure 1-3: data & command modes note: for detailed information on the ascii comm ands you use to configure the bluetooth module, refer to the bluetooth command reference & advanced information user?s guide . uart bluetooth interface bluetooth module command mode $$$ $$$ a b user data bluetooth host a b
RN-4142-EK-UG www.rovingnetworks.com version 1.0 12/10/12 page 7 the default configuration fo r the bluetooth device is: ? bluetooth slave mode ? keyboard default authentication mode (no pin code required) ? serial port 115,200 kbps baud rate, 8 bits, no parity, 1 stop bit ? serial port flow control disabled ? low power mode off you configure the device by putting it into command mode and sending ascii commands over a serial port or the bluetooth link. once you c hange the configuration pa rameters, they persist until you change them or perform a factory reset. there are two ways to configure the bluetooth module: ? local configuration using your computer?s usb port ? via bluetooth you need a terminal emulator to complete the setup. 4.2 configure the module locally using the usb port set up the rn-41-ek or rn-42-ek hardware as described in ?hardware setup? on page 5 . with the bluetooth device connected and powered on, run a terminal emulator and open the com port to which the cable is connected. you should co nfigure the virtual com port connected to the rn-41-ek or rn-42-ek usb interface with the default settings (115,200 kbps baud, no parity, 8 bits, 1 stop bit). you can use command mode through the uart interface via the usb connector at any time when the device does not have a bluetooth connec tion, as well as under certain conditions. if the device is in configuration mode and a connec tion occurs, the device exits configuration mode and data passes back and forth from the remote device. 4.3 enter command mode to enter command mode, launch a terminal emul ator and specify the m odule?s default settings. table 4-1 shows the serial port settings. type $$$ into the terminal emulator to enter command mode. the module returns the string cmd , which indicates that your connection and terminal settings are correct. while in command mode, the de vice accepts ascii bytes as commands. note: suggested terminal emulator programs are teraterm (windows os) or coolterm (mac os-x). note: if the device is in auto-connect mast er mode, you cannot enter command mode when connected over bluetooth. see ?operating modes? on page 9 for more infor- mation on the various operating modes. table 4-1: serial port settings setting value port com port to which you attached the module baud rate 115200 data rate 8 bits patiry none stop bits 1 flow control none
RN-4142-EK-UG www.rovingnetworks.com version 1.0 12/10/12 page 8 when you power up the module, you must enter command mode within a 60 second configura- tion window; otherwise, the module goes into fast data mode in which all characters are ignored including $$$ . if the configuration timer expires while the device is in command mode, the device does not go into fast data mode after exiti ng command mode. when you enter a valid command, the module returns aok . it returns err for an invalid command and ? for unrecognized com- mands. type h to see a list of commands. a quick check to confirm that you are in command mode is to type the x command after entering command mode. this command shows t he a summary of the module?s current settings, such as the bluetooth name, device class, and serial port settings. see figure 1-2 . to return to data mode, type --- or reset the device and re-connect. figure 1-4: view current settings
RN-4142-EK-UG www.rovingnetworks.com version 1.0 12/10/12 page 9 4.4 operating modes the bluetooth device has several operating modes, which you set using the sm command in command mode. ? slave mode (sm,0) ?default mode, in which other bluetooth devices can discover and connect to the device. you can also ma ke outbound connections in this mode. ? master mode (sm,1) ?in this low-speed connection mode, the device makes connections when a connect command ( c ) is received. this command can also contain the bluetooth address of the remote device. if a device is not specified, the m odule uses the stored remote address. the connection can be broken if the special break character or string is sent (use the so command to set the break character). this mode is useful when you want the device to initiate connections (not receive them). in this mode, the device is not dis- coverable or connectable. ? trigger mode (sm,2) ?in this low-speed connection m ode, the device makes connections automatically when a character is received on the serial port (uart). the connection con- tinues as long as characters are received on either end. the device has a configurable tim- eout (which you set using the st command) that disconnects th e module after the specified number of seconds of inactivity (1 to 255) or a configurable break character is received. ? auto-connect master mode (sm,3) ?in this mode, the device makes connections automat- ically on power-up and re-connects when the c onnection is lost. this mode can be set by command, or by setting the external dipswi tch 3 during power up. if an address is not stored, the device performs an inquiry proce ss and the first device fo und that matches the cod is stored. in this mode , high-speed data is passed witho ut being interpreted; there- fore, the connection cannot be broken via comm ands or software break characters. if a dis- connect occurs, the device attempts to re-connect until successful. ? auto-connect dtr mode (sm,4) ?this mode must be set by command. it operates like auto-connect master mode, except that yo u control connection and disconnection with dipswitch 3. turning the dipswitch on init iates the auto-connect process; turning the dipswitch off causes a disconnect. ? auto-connect any mode (sm,5)? this mode must be set by command. this mode oper- ates like auto-connect dtr mode, except that ea ch time the dipswitch is set, an inquiry is performed and the first device found is con nected. the stored a ddress is not used, and the address found is never stored. ? pairing mode (sm,6 )?in this mode, the device attempts to connect with the remote device matching the store remote address. you set the remote address using the sr command. note: in all master modes, the device cannot be discovered or configured remotely over bluetooth.
RN-4142-EK-UG www.rovingnetworks.com version 1.0 12/10/12 page 10 4.5 configuration switches the evaluation boards have small configurati on switches on the bottom. you need a paper clip or small screwdriver to flip them. holding the boa rd with the pcb antenna facing to the right, refer to figure 1-3 for the switch numbering and on/off positions. figure 1-5: config uration switches table 4-2 describes the functions controlled by the switches. 1 2 3 4 off on table 4-2: configuratio n switch functions switch function default (off) description 1 restore fac- tory defaults do not restore factory defaults. turn on the s witch, power up the evaluation kit, and tog- gle the switch on-off-on-of f-on to return the mod- ule to its factory settings. the green (labeled as s) led blinks quickly for a moment and then continues to blink about once per second. 2 automatic dis- covery automatic discovery is turned off. in slave mode, this switch sets a special class of device that is used by the master to auto connect. if switch 3 also turned on, the module performs a search, stores, and connects to a remote roving networks bluetooth device that has switch 2 turned on. 3 automatic master automatic master is turned off. with this s witch turned on, the module acts as bluetooth master and auto-connects to a stored remote address. you must first set the bluetooth address of the slave device using the sr command or using instant cable replacement settings. 4 default baud rate with this switch turned off, the default 115 k baud rate is over- ridden by software baud rate configuration commands. if this switch is turned on, the baud rate is 9600 and the module ignores the software configuration.
RN-4142-EK-UG www.rovingnetworks.com version 1.0 12/10/12 page 11 4.6 making a bluetooth connection by default, the bluetooth module acts as a slav e and the pc is the master. you connect to the bluetooth module using your computer?s bluet ooth device manager, which varies depending on the operating system. regardless of the operating syst em, the process is the same: discovery, pairing, and connecting. 4.6.1 discovery when you turn on the rn-41-ek or rn-42-ek, the gr een led (labeled as s) blinks once per sec- ond and the module is discoverable. open yo ur pc?s bluetooth device manager and choose to add a new device. the bluetooth device manager?s icon is located in the bottom right corner of your screen in the taskbar for windows and in th e upper right corner for mac os-x. the bluetooth device manager displays a list of discove rable bluetooth device. the board displays as fire- fly- xxxx , where xxxx are the last 2 bytes of the device?s bluetooth address. see figure 1-4 . figure 1-6: discovery - add a bluetooth device 4.6.2 pairing to pair with the evaluation boar d, double-click the board?s name in the list. the firmware auto- matically stores up to 8 pairings from remote hosts in a first in, first out fashion. the evaluation board?s default authentication mode is keyboard (no pin code required). however, most pcs require authentication and display a pin co de. if you are using a bluetooth usb dongle (e.g., rn-usb-t), your pc prompts you to choose how you want to pair. figure 1-5 shows exam- ples of pairing with and without a pin code. note: if your pc displays a pin code and asks you to confirm if it is correct, choose yes .
RN-4142-EK-UG www.rovingnetworks.com version 1.0 12/10/12 page 12 figure 1-7: pairing - comparing pin codes & pairing options when the bluetooth device manager completes pairin g, it issues a message that the bluetooth device is installed on com x where com x is unique to your computer. in some cases, the blue- tooth device manager creates two com ports; in this situation, only use the com port labeled outgoing. figure 1-6 shows example com port settings. figure 1-8: pairing - bluetooth com port settings
RN-4142-EK-UG www.rovingnetworks.com version 1.0 12/10/12 page 13 if the remote bluetooth device does not require authentication, a connection can occur without the pairing process. however the bluetooth specificat ion requires that if either device involved in the pairing process requires aut hentication, the other device must participate to ensure a secure link. roving networks modules default to an open mode, such that the module does not require authentication. see ?security modes? on page 15 for more information on using pass keys. the module may use simple secure pairing (ssp) if it is attempting to pair with devices that sup- port the bluetooth specification version 2.1 + e dr. ssp does not require the user to remember the pin code, but it asks to confirm the 6-digi t number if the device ha s a display capability. 4.6.3 connecting in most cases, you connect from another dev ice to the rn-41-ek or rn-42-ek as an outgoing bluetooth connection. you can also make an incoming connection in which the evaluation board initiates the connection to the remote device. 4.6.3.1 outgoing connections to establish an outgoing bluetooth connection from a pc to the rn-41-ek or rn-42-ek board, open the module?s outgoing com port from your application or a terminal emulator. when you establish a connection by opening the com port, the evaluation board?s green led (labeled as s) goes on solid (not blinking) to indicate that the device is connected . the device remains con- nected until you close the com port, remove power from the board, or terminate the connection using the k,1 command. refer to the bluetooth command reference & advanced information user?s guide for more information on using commands. once connected, the device is in data mode allowing data to flow in both directions. the board?s red led (labeled as a) blinks once per second when data is transferred over the uart. for con- figuration and programming, the device must be in command mode. see ?enter command mode? on page 7 for more information. 4.6.3.2 incoming connections for an incoming connection you use the port spec ified in your bluetooth settings as incoming (refer back to figure 1-6 ). the pc or host listens for an incoming connection from the remote blu- etooth device, in this case t he rn-41-ek or rn-42-ek. perform the following steps to make in incoming connection. 1. you need the mac address of the pc?s blue tooth radio to connect from the rn-41-ek or rn-42-ek to the host pc. open the pc?s bluetooth advanced settings to find the mac address. see figure 1-7 . note: only one client can connect to a slave device at a time. as a master, the device can make multiple connections, but only in a point-to-point, serialized fashion. the rn41 and rn42 modules do not currently support multi-point master mode.
RN-4142-EK-UG www.rovingnetworks.com version 1.0 12/10/12 page 14 figure 1-9: pc?s blue tooth radio mac address 2. pair your evaluation board with the pc as described in ?pairing? on page 11 . 3. open a terminal (called terminal a in this ex ample) and connect it to the evaluation board?s outgoing com port. you can run this terminal on the host pc or another computer. 4. open a second terminal (called terminal b in this example) on the host pc to listen for the incoming bluetooth connection using the incoming com port number. 5. type c, < mac address > in terminal a to establish an spp connection to the host pc. see figure 1-8 for an example connection. 6. try the following commands: ? $$$ to enter command mode ? so,% to enable status message to see connect/disconnect conditions ? r,1 to reboot ? $$$ to re-enter command mode ? + to enable local echo ? c, < mac address > to attempt a connection with a remote device characters you type in terminal b are sent ov er bluetooth to the host pc and appear in ter- minal a. any characters entered in terminal a are transmitted to terminal b. 7. to kill the connection, type the k,1 command in terminal b.
RN-4142-EK-UG www.rovingnetworks.com version 1.0 12/10/12 page 15 figure 1-10: terminals a & b 4.7 security modes the bluetooth module supports authentication. if the local or remote bluetooth device has authentication enabled, a pin code is required the first time a connection is attempted. the pin code is a series of numbers or characters from 1 to 16 characters in length. after you enter the pin code, the bluetooth devices co mpare them. if they match, a link key is generated and stored. usually, but not always, the remote device stores the link key. for subsequent connections, the devices compare link keys. if they are correct, yo u do not need to re-enter the pin code. if the remote device is a pc or pda, the user generally is prom pted to enter this pin code. to remove the stored link key on the remote device, you typically ?unpair? or remove the device from the bluetooth manager. you can change the pin code to remove the link key on the bluetooth module, forcing a new pin code exchange to occur upon subsequent connection attempts. note: only one master can connect to the bluetooth module at a time.
RN-4142-EK-UG www.rovingnetworks.com version 1.0 12/10/12 page 16 5.0 resources & re lated documents for more informatio n, refer to the following sources: ? rn41/rn41n class 1 bluetooth module data sheet ? rn42/rn42n class 2 bluetooth module data sheet ? bluetooth command reference & advanced information user?s guide 6.0 document revi sion history 6.1 version 1.0 initial release. 7.0 ordering information table 7-1 provides ordering information for the evaluation kits. go to http://www.rovingnetworks.com for current pricing and a list of distributors carrying roving networks products. table 7-1: evaluation kit ordering information part number description rn-41-ek evaluation kit for the rn41 (class 1) bluetooth module. rn-42-ek evaluation kit for the rn42 (class 2) bluetooth module.
RN-4142-EK-UG www.rovingnetworks.com version 1.0 12/10/12 page 17 appendix a: rn-41-ek & rn-42-ek schematic figure 1-9 shows the schematic for the rn-42-ek evaluation board. the rn41 and rn42 mod- ules are pin compatible; therefore, the schematic applies to both boards. figure 1-11: rn-41-ek & rn-42-ek schematic tx d rx d gnd 1 spi _mosi 2 pi o6 3 pi o7 4 reset 5 spi _sck 6 pcm_cl k 7 pcm_sync 8 pcm_i n 9 pcm_out 10 vdd 11 gnd 12 uart_rx 13 uart_tx 14 uart_rts 15 uart_cts 16 usb_d+ 17 usb_d- 18 pi o2 19 pi o3 20 pi o5 21 pi o4 22 spi _cs# 23 spi _mi so 24 gnd 28 gnd 29 aio0 30 pio8 31 pio9 32 pio10 33 pio11 34 aio1 35 shield 0 m1 rn42 module spi _mi so spi _mosi spi _sck spi _ss rt s ct s reset _n pi o6 pi o7 pi o4 pi o5 pi o3 pi o2 aio1 aio0 pio11 pio10 pio9 pio8 1 2 3 4 5 6 j3 spi master spi _mi so spi _mosi spi _sck spi _ss 3.3v 3.3v pcm_cl k pcm_sync pcm_out pcm_i n 100k r17 300k r18 100k r16 300k r15 v b1 v b2 a io0 a io1 1 2 3 4 5 6 7 8 9 10 11 12 j1 header 1 1 2 3 4 5 6 7 8 9 10 11 12 j2 header 2 pi o6 pi o7 reset _n rx d tx d rt s ct s pi o4 pi o3 pi o2 pi o11 pi o10 pi o9 pi o8 3.3v vb1 vb2 shdn d_n d_p txd rxd rts cts vbus reset 18 3v 3out 16 usbdp 14 usbdm 15 gnd 17 cbus2 10 cbus1 21 vccio 1 cbus3 11 cbus4 9 cbus0 22 gnd 20 ri 3 dcd 7 dsr 6 dtr 31 cts 8 rts 32 rxd 2 txd 30 vcc 19 osci 27 osco 28 agnd 24 test 26 gnd 4 thp ad 33 ft232rq u3 100nf c6 100nf c5 100nf c4 gnd 5 d+ 3 d- 2 vbus 1 mtab 6 usb mini b j4 3k3 r12 3k3 r13 3k3 r11 3k3 r14 vbus 3.3v vbus vi n 1 gnd 2 shdn 3 byp 4 vout 5 u1 tc1185 1uf c2 1uf c1 shdn 3k3 r1 1 2 3 4 s1 3k3 r10 3k3 r9 3k3 r8 3k3 r7 3.3v pi o4 pi o3 pi o6 pi o7 red led d2 activity pi o5 3.3v pi o8 green led d1 connection status 470 r2 470 r3
RN-4142-EK-UG www.rovingnetworks.com version 1.0 12/10/12 page 18 notes:


▲Up To Search▲   

 
Price & Availability of RN-4142-EK-UG

All Rights Reserved © IC-ON-LINE 2003 - 2022  

[Add Bookmark] [Contact Us] [Link exchange] [Privacy policy]
Mirror Sites :  [www.datasheet.hk]   [www.maxim4u.com]  [www.ic-on-line.cn] [www.ic-on-line.com] [www.ic-on-line.net] [www.alldatasheet.com.cn] [www.gdcy.com]  [www.gdcy.net]


 . . . . .
  We use cookies to deliver the best possible web experience and assist with our advertising efforts. By continuing to use this site, you consent to the use of cookies. For more information on cookies, please take a look at our Privacy Policy. X